Providing Payment Account Information Associated With A Digital Wallet Account To A User At A Merchant Point Of Sale Device

ABSTRACT

In an example embodiment, the user initiates a digital wallet transaction at a point of sale (“POS”) terminal of a merchant system. The POS terminal receives payment account information options associated with the user&#39;s digital wallet account from the account management system to display to the user. The user selects one or more payment account information options via a user interface of the POS terminal. The account management system receives an indication of the user&#39;s one or more selections, generates one or more payment tokens based on the corresponding selected payment account information options, and transmits the one or more payment tokens to the POS terminal for use in a transaction. The POS terminal communicates with one or more issuer systems associated with the selected payment account information options to process the transaction using corresponding payment tokens. The user receives a transaction receipt at the POS terminal.

TECHNICAL FIELD

The present disclosure relates to improving user convenience in digitalwallet transactions by providing payment account information of theuser's digital wallet account to a merchant point of sale device foruser selection.

BACKGROUND

Digital wallet account services enable a user to electronically storepayment information in a user's digital wallet account. In paymenttransactions involving a digital wallet account, the payment informationis often stored on an application or a module of a user computingdevice. Often, a user must have the user computing device present whenconducting in-store digital wallet transactions with a point of saledevice because the payment information is communicated from the usercomputing device to the point of sale device. For example, the usercomputing device and point of sale device may establish a wirelesscommunication channel, such as a Bluetooth, Wi-Fi, or NFC communicationchannel to transmit payment information from the user computing deviceto the point of sale device. However, such a process may be inconvenientto the user because the user must physically carry a user computingdevice, such as a mobile phone, to conduct a digital wallet transaction,which may deter users from using digital wallet accounts. Currenttechnology does not provide for providing direct access to paymentaccount information associated with a user's digital wallet account at amerchant system point of sale device interface for selection by a userfor use in a transaction at the point of sale device.

SUMMARY

Techniques herein provide computer-implemented methods to provide accessto payment account information associated with a user's digital walletaccount to the user at a merchant system point of sale interface for usein a transaction. The user initiates a digital wallet transaction at apoint of sale (“POS”) terminal of a merchant system and verifies theuser's identity at the point of sale terminal. The POS terminal receivespayment account information options associated with the user's digitalwallet account from the account management system and displays thepayment account information options to the user. The user selects one ormore payment account information options via a POS terminal userinterface. The account management system receives an indication of theuser selection of the one or more payment account information optionsfrom the POS terminal, generates one or more payment tokens based on thecorresponding selected payment account information options, andtransmits the payment token to the POS terminal for use in atransaction. The point of sale terminal communicates with one or moreissuer systems associated with the selected payment account informationoptions to process the transaction using the one o more correspondingpayment tokens. The user receives a transaction receipt at the POSterminal.

In certain other example aspects described herein, systems and acomputer program products to provide access to payment accountinformation associated with a user's digital wallet account to the userat a merchant system point of sale interface for use in a transactionare provided.

These and other aspects, objects, features, and advantages of theexample embodiments will become apparent to those having ordinary skillin the art upon consideration of the following detailed description ofillustrated example embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a system for providing digitalwallet payment account information directly to a merchant system pointof sale terminal for user selection, in accordance with certain exampleembodiments.

FIG. 2 is a block flow diagram depicting a method for providing digitalwallet payment account information directly to a merchant system pointof sale terminal for user selection, in accordance with certain exampleembodiments.

FIG. 3 is a block flow diagram depicting a method for registering for adigital wallet account with an account management system, in accordancewith certain example embodiments.

FIG. 4 is a block flow diagram depicting a method for initiating, by auser, a transaction at a merchant system point of sale terminal, inaccordance with certain example embodiments.

FIG. 5 is a block flow diagram depicting a method for providing useridentification information and user verification information at a pointof sale terminal for verification by an account management system, inaccordance with certain example embodiments.

FIG. 6 is a block flow diagram depicting a method for providing userverification information received at a point of sale terminal to anaccount management system, in accordance with certain exampleembodiments.

FIG. 7 is a block flow diagram depicting a method for selecting apayment account information option associated with a user digital walletaccount via a point of sale terminal user interface, in accordance withcertain example embodiments.

FIG. 8 is a block flow diagram depicting a method for communicating withan issuer system to process a transaction using a payment token, inaccordance with certain example embodiments.

FIG. 9 is a block diagram depicting a computing machine and module, inaccordance with certain example embodiments.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

The example embodiments described herein provide computer-implementedtechniques for providing access to payment account informationassociated with a user's digital wallet account to the user at amerchant system point of sale interface for use in a transaction. In anexample embodiment, a user registers for a digital wallet account withan account management system. The user initiates a digital wallettransaction at a point of sale terminal of a merchant system andverifies the user's identity at the point of sale terminal. The point ofsale terminal receives payment account information options associatedwith the user's digital wallet account from the account managementsystem and displays the payment account information options to the user.The user selects a payment account information option via the point ofsale user interface. The account management system receives anindication of the user selection of the payment account informationoption from the point of sale terminal, generates a payment token basedon the selected payment account information, and transmits the paymenttoken to the point of sale terminal for use in a transaction. The pointof sale terminal communicates with an issuer system associated with thepayment account information to process the transaction using the paymenttoken. The user receives a transaction receipt at the point of saleterminal.

In an example embodiment, a user registers for a digital wallet accountwith an account management system. For example, the user accesses anaccount management system website from a user computing device toestablish the digital wallet account via the website. In an example, adigital wallet application is downloaded from the account managementsystem website onto a user computing device associated with the user.The user transmits payment account information to enter into the digitalwallet account via the digital wallet application. For example, the usertransmits payment account information corresponding to one or morecredit accounts, debit accounts, bank accounts, coupons, offers, rewardspoints accounts, loyalty card accounts, or other applicable accounts.For example, for a credit account, the user enters the credit cardnumber associated with the credit account, the expiration date of thecredit card, a CVC number, a name associated with the account, and/or azip code associated with the account. In another example, for a coupon,the user enters a coupon code associated with the coupon or otherwisecaptures an image of a barcode associated with the coupon via the usercomputing device. The account management system receives the userpayment account information and saves the user payment accountinformation in the digital wallet account associated with the user.

In an example embodiment, a user enters a merchant system location,selects one or more items for sale, and approaches a merchant systempoint of sale terminal to check out. The point of sale terminal presentsthe user with one or more payment options comprising an option to checkout using a digital wallet account. For example, the point of saleterminal presents the user with the options to pay via digital walletaccount, debit card, credit card, bank account, cash, check, storeaccount, or any other relevant or appropriate payment option for use inan in-store transaction between the user and the merchant system. Theuser selects an option to check out using the user's digital walletaccount and the point of sale terminal displays a request for useridentification. The user enters user identification via the userinterface at the point of sale terminal. In an example embodiment, theuser identification information enables the account management systemand/or the merchant system to identify the user's name and/or the user'sdigital wallet account. For example, the user identification informationmay comprise a user's first and last name, a user name associated withthe user's digital wallet account, a digital wallet account number, orother relevant user identification information. In another example, theuser identification information comprises biometric data that the usersubmits via the point of sale terminal, such as a fingerprint, retinalscan, or a voice recording. The point of sale system transmits thereceived user identification information to the account managementsystem along with a payment information request.

In an example embodiment, the account management system receives theuser identification information and the payment information request. Theaccount management system identifies and accesses the user's digitalwallet account using the received identification information. In anexample embodiment, the account management system transmits a requestfor user verification information to the point of sale terminal to bedisplayed to the user. The point of sale terminal displays the requestand the user provides verification information to the point of saleterminal. In an example, verification information comprises a PIN, apassword, the selection of a particular image out of a group of imagescomprising at least the particular image, a fingerprint, a retinal scan,a voice input, and/or any other input of the user that can be used bythe account management system to verify the identity of the userassociated with the user identification information and/or the user'sdigital wallet account. In an example embodiment, the account managementsystem receives the user verification information at the time the userregisters for a digital wallet account and associates the userverification information with the digital wallet account. In thisexample embodiment, the account management system verifies the userverification information received from the point of sale terminalagainst the user verification information associated with the digitalwallet account. If the received verification information is invalid, theaccount management system subsequently requests user verificationinformation via the point of sale terminal or cancels the transaction.If the received verification information is valid, the accountmanagement system transmits payment information options associated withthe user's digital wallet account to the point of sale terminal.

In an example embodiment, the point of sale terminal receives anddisplays the payment information options. In an example, the paymentinformation options received and/or displayed by the point of saleterminal are incomplete and/or obfuscated. For example, payment accountinformation associated with a user comprises an account type and number,Issuer A Credit 8800-0077-6600-0055, but the payment information optionreceived by the point of sale terminal and/or displayed to the userreads “Issuer A Credit xxxx-xxxx-xxxx-0055”, only comprising the issuername associated with the account (Issuer A), the account type (Credit),and the last four digits of the account number (0055). In an exampleembodiment, the user selects a particular payment information optionfrom available payment information options associated with the user'sdigital wallet account via the user interface of the point of saleterminal. In another example embodiment, the user selects two or morepayment information options from the available payment informationoptions. For example, the user may select a credit account paymentinformation option, a coupon payment information option, and a rewardspoints payment information option to use in the transaction. The pointof sale terminal communicates an indication of the user's one or moreselections of the payment information option(s) to the accountmanagement system.

In an example embodiment, the account management system receives theindication of the user selection of the payment information option andgenerates a payment token based on the payment account informationassociated with the payment information option selected by the user. Anexample payment token comprises information that enables an issuersystem to identify a user payment account associated with the issuersystem and process a payment authorization request received from thepoint of sale terminal associated with a transaction involving the userpayment account. For example, the payment token may comprise an actualaccount number or a virtual account number that the issuer system canuse to find the actual account number in a database of the issuersystem. The account management system transmits the payment token to thepoint of sale terminal.

The point of sale terminal communicates with the issuer system toprocess the transaction using the payment token. In an exampleembodiment, the issuer system comprises a credit card issuer, a bank orfinancial institution system, a coupon issuer, an advertiser, or othersystem with whom the user has an account or with whom the merchant mayexpect reimbursement for part or all of the value of the transactioninitiated by the user at the point of sale terminal. In an exampleembodiment, the point of sale terminal communicates with two or moreissuer systems to process the transaction using two or more paymenttokens. For example, the point of sale terminal receives a first paymenttoken associated with a coupon and a second payment token associatedwith a credit card account. In this example, the point of sale systemfirst communicates with a coupon issuer system to process the couponusing the first payment token, discounts the value of the coupon fromthe transaction, then communicates with a credit card issuer system toprocess a second transaction for the value of the user's outstandingbalance. An example issuer system receives the payment token, identifiesa user payment account or other applicable account based on the paymenttoken, and approves or denies the payment authorization request. Thepoint of sale terminal prints a receipt at the point of sale terminal orotherwise transmits the receipt to the user.

By using and relying on the methods and systems described herein, theaccount management system and the merchant system point of sale deviceenable the user to select payment account information associated withthe user's digital wallet account directly at the point of sale terminalfor use in a transaction. Additionally, by enabling the point of saleterminal to receive user payment account information options associatedwith the user's digital wallet account from the account managementsystem to display to the user to select for use in a transaction, theuser does not have to produce a physical digital wallet payment card ora user computing device at the point of sale terminal. As such, thesystems and methods described herein may provide a convenience to theuser.

Example System Architecture

Turning now to the drawings, in which like numerals indicate like (butnot necessarily identical) elements throughout the figures, exampleembodiments are described in detail.

FIG. 1 is a block diagram depicting a system 100 for providing digitalwallet payment account information directly to a merchant system POSterminal for user selection, in accordance with certain exampleembodiments. As depicted in FIG. 1, the system 100 includes networkcomputing devices/systems 110, 120, 130, 140, and 150 that areconfigured to communicate with one another via one or more networks 160.In some embodiments, a user associated with a device must install anapplication and/or make a feature selection to obtain the benefits ofthe techniques described herein.

In example embodiments, the network 160 can include a local area network(“LAN”), a wide area network (“WAN”), an intranet, an Internet, storagearea network (“SAN”), personal area network (“PAN”), a metropolitan areanetwork (“MAN”), a wireless local area network (“WLAN”), a virtualprivate network (“VPN”), a cellular or other mobile communicationnetwork, Bluetooth, Bluetooth low energy, NFC, or any combinationthereof or any other appropriate architecture or system that facilitatesthe communication of signals, data, and/or messages. Throughout thediscussion of example embodiments, it should be understood that theterms “data” and “information” are used interchangeably herein to referto text, images, audio, video, or any other form of information that canexist in a computer-based environment.

Each network computing device 110, 120, 130, 140, and 150 includes adevice having a communication module capable of transmitting andreceiving data over the network 160. For example, each network computingdevice 110, 120, 130, 140, and 150 can include a server, desktopcomputer, laptop computer, tablet computer, a television with one ormore processors embedded therein and/or coupled thereto, smart phone,handheld computer, personal digital assistant (“PDA”), or any otherwired or wireless, processor-driven device. In the example embodimentdepicted in FIG. 1, the network computing devices 110, 120, 130, 140,and 150 are operated by users 101, merchant system 120 operators,account management system 130 operators, acquirer system 140 operators,and issuer system 150 operators, respectively.

An example user computing device 110 comprises a communicationapplication 111, a web browser 112, a data storage unit 115, a digitalwallet application 117, and a user interface 119.

In an example embodiment, the user 101 can use a communicationapplication 111, such as a web browser 112 application or a stand-aloneapplication, to view, download, upload, or otherwise access documents orweb pages via a distributed network 160. In an example embodiment, thecommunication application 111 can interact with web servers or othercomputing devices connected to the network 160, including the usercomputing device 110 and a web server 131 of a merchant system 130.

In an example embodiment, the web browser 112 can enable the user 101 tointeract with web pages using the user computing device 110. In anexample embodiment, the user 101 may access a website 133 of the accountmanagement system 130 to establish a digital wallet account with theaccount management system 130 via the web browser 112. In an exampleembodiment, the user 101 may access the user's 101 digital walletaccount maintained by the account management system 130 via the webbrowser 112. In another example embodiment, the user 101 may enterpayment information into the user's 101 digital wallet account via theweb browser 112. In certain example embodiments described herein, one ormore functions performed by the digital wallet application 117 may alsobe performed by a web browser 112 application associated with theaccount management system 130.

In an example embodiment, the data storage unit 115 comprises a local orremote data storage structure accessible to the user computing device110 suitable for storing information. In an example embodiment, the datastorage unit 115 stores encrypted information, such as HTML5 localstorage. In an example embodiment, the data storage unit 115 resideswithin a secure element (not depicted).

In an example embodiment, the digital wallet application 117 is aprogram, function, routine, applet, or similar entity that exists on andperforms its operations on the user computing device 110. In certainembodiments, the user 101 must install the digital wallet application117 and/or make a feature selection on the user computing device 110 toobtain the benefits of the techniques described herein. In an exampleembodiment, the digital wallet application 117 communicates with theaccount management system 130. In an example embodiment, a user 101downloads the digital wallet application 117 from an account managementsystem website 133 onto a user computing device 110. In an exampleembodiment, a user 101 may access the user's 101 digital wallet account,add new payment account information to the digital wallet account, editpayment account information in the digital wallet account, or deleteexisting payment account information from the digital wallet account viathe digital wallet application 117.

In certain example embodiments described herein, one or more functionsperformed by the digital wallet application 117 resident on the usercomputing device 110 may also be performed by a web browser 112application associated with the account management system 130. Incertain example embodiments described herein, one or more functionsperformed by the account management system 130 may also be performed bythe digital wallet application 117. In certain example embodimentsdescribed herein, one or more functions performed by the web browser 112application associated with the account management system 130 may alsobe performed by the digital wallet application 117.

In certain example embodiments described herein, the digital walletapplication 117 maintains periodic or constant communication with theaccount management system 130 via the network 160. In certain exampleembodiments, the digital wallet application 117 and is able to send andreceive data associated with the user's 101 digital wallet account toand from the account management system 130 when appropriate. Forexample, the digital wallet application 117 may communicate user 101interactions with the digital wallet application 117 via the userinterface 119 to the account management system 130, such as a user 101selection of an option to add a payment account information. In thisexample, the digital wallet application 117 may communicate financialaccount information entered by the user 101 on the user computing device110 to the account management system 130 for saving in the user's 101digital wallet account.

In an example embodiment, the user interface 119 may be a touch screen,a voice-based interface or any other interface that allows the user 101to provide input and receive output from an application or module on theuser computing device 110. In an example embodiment, the user interface119 enables the user 101 to interact with the digital wallet application117 or a web browser 112 application associated with the accountmanagement system 130. For example, the user 101 may actuate one or moreobjects on the user interface 119 to instruct the digital walletapplication 117 and/or web browser 112 application to add, edit, ordelete payment account information to/from the user's 101 digital walletaccount.

In certain example embodiments, at a time after a user 101 selects anoption to check out using a digital wallet account via the merchant POSterminal user interface 129, the merchant POS terminal 123 may establisha wireless communication channel with a user computing device 110 of theuser 110 to receive a hardware identifier associated with the usercomputing device 110 for user 101 identification purposes. In thisexample embodiment, the user 101 operating the user computing device 110may select an option on the user interface 119 to allow the wirelesscommunication channel to be established. For example, the user 101 viewsa request on the user computing device 110 that says “do you wish toestablish a wireless connection with Merchant A?” and selects an objecton the user interface 119 that says “yes, I wish to establish a wirelessconnection with Merchant A.”

An example merchant system 120 comprises a point of sale (“POS”)terminal 123, an example POS terminal 123 comprising a data storage unit125, an application 127, and a user interface 129.

In an example embodiment, the merchant system 120 comprises one or morePOS terminals 123 at one or more physical locations of the merchantsystem 120. For example, the merchant system 120 is a supermarket chainand comprises several physical locations, each location comprising oneor more POS terminals 123.

An example merchant system 120 comprises at least one point of sale(“POS”) terminal 123 that is capable of processing a purchasetransaction initiated by a user for example, a cash register. In anexample embodiment, the merchant operates a commercial store and theuser indicates a desire to make a purchase by presenting a form ofpayment at the POS terminal 123. In certain example embodiments, the POSterminal 123 communicates directly with the account management system130, enabling the user 101 to directly select payment accountinformation options from the user's 101 digital wallet account from thePOS terminal user interface 129. In an example embodiment, the POSterminal 123 operates as a normal POS device, and the user 101 and/or amerchant system operator is able to scan or enter one or more items thatthe user desires to purchase.

An example data storage unit 125 residing on the POS terminal 123comprises a local or remote data storage structure accessible to the POSterminal 123 suitable for storing information. In an example embodiment,the data storage unit 125 stores encrypted information, such as HTML5local storage. In an example embodiment, the data storage unit 125resides within a secure element (not depicted) in the POS terminal 123.

An example POS terminal application 127 comprises a program, function,routine, applet, or similar entity that exists on and performs itsoperations on the POS terminal 123. In certain embodiments, the merchantsystem 130 operator must install the application 127 to obtain thebenefits of the techniques described herein. In an example embodiment,the POS terminal application 127 instructs the user interface 129 topresent the user 101 with one or more payment options for a transaction.In an example embodiment, the POS terminal application 127 receives anindication of a selection of a particular payment option of the one ormore payment options from the user interface 129. For example, the POSterminal application 127 receives an indication that the user 101selected an option on the user interface 129 to initiate a digitalwallet transaction using a digital wallet account associated with theaccount management system 130. In an example embodiment, the POSterminal application 127 instructs the user interface 129 to display arequest for the user to enter user 101 identification information. Inthis example embodiment, the POS terminal application 127 receives user101 identification information entered by the user 101 at the userinterface 129. In another example embodiment, instead of instructing theuser interface 129 to display a request for the user 101 identificationinformation, the POS terminal application 127 instructs the POS terminal123 to establish a wireless communication channel with a user computingdevice 110 to receive user 101 identification information comprising ahardware identifier of the user computing device 110.

In an example embodiment, the POS terminal application 127 transmits apayment information request and the identification information to theaccount management system 130. In an example embodiment, the POSterminal application 127 receives, from the account management system130, a request for the user 101 to transmit user 101 verificationinformation. In an example embodiment, the POS terminal application 127instructs the user interface 129 to display a request for user 101verification information to the user 101. In this example embodiment,the POS terminal application 127 receives user 101 verificationinformation entered by the user 101 at the user interface 129. In anexample embodiment, the POS terminal application 127 transmits the user101 verification information to the account management system 130. In anexample embodiment, the POS terminal application 127 receives one ormore payment account information options from the account managementsystem 130. In an example embodiment, the POS terminal application 127instructs the user interface 129 to display the one or more receivedpayment account information options to the user 101. In an exampleembodiment, the POS terminal application 127 receives an indication fromthe user interface 129 of a user 101 selection of one or more displayedpayment account information options. In an example embodiment, the POSterminal application 127 transmits the indication of the user 101selection of the one or more payment account information options to theaccount management system 130.

In an example embodiment, the POS terminal application 127 receives,from the account management system 130, one or more payment tokensgenerated by the account management system 130 corresponding to the oneor more user 101 selected payment account information options. In anexample embodiment, the POS terminal application 127, for each receivedpayment token, communicates with an issuer system 150 associated withthe payment account information associated with the payment token toprocess a transaction using the payment token. For example, the POSterminal application 127 may communicate with one or more credit cardissuer systems 150, coupon issuer systems 150, bank issuer systems 150,or other appropriate issuer systems 150. In an example embodiment, foreach issuer system 150 with which the POS terminal application 127communicates to process a transaction, the POS terminal application 127receives a notice of an approved or declined payment transaction. In anexample embodiment, the POS terminal application 127 instructs the POSterminal 123 to print or send a transaction receipt based on the receiptof the one or more notices of an approved or declined paymenttransactions associated with the user 101 initiated transaction.

An example user interface 129 may be a touch screen, a voice-basedinterface or any other interface that allows the user 101 to provideinput and receive output from an application or module on the POSterminal 123. In an example embodiment, the user interface 129 enablesthe user 101 to select, from a plurality of displayed payment options,an option to check out using a digital wallet account associated withthe account management system 130. In an example embodiment, the userinterface 129 displays a request for user 101 identification informationand enables the user 101 to enter the user 101 identificationinformation into the POS terminal 123. In an example embodiment, theuser interface 129 displays a request for user 101 verificationinformation and enables the user 101 to enter the user 101 verificationinformation into the POS terminal 123. For example, the user interface129 may comprise a touch screen keyboard, an external keyboard, afingerprint scanner, a voice recorder, a retinal scanner, or otherappropriate or relevant hardware to receive a user 101 input of user 101identification information and/or user 101 verification information.

In an example embodiment, the user interface 129 displays one or morepayment account information options received by the POS terminal 123from the account management system 130 and enables the user 101 toselect one or more of the displayed payment account information optionsfor use in the user 101 initiated transaction. In an example embodiment,the user interface 129 communicates with the POS terminal application127. For example, the user interface 129 receives instructions todisplay requests or display options to select from the POS terminalapplication 127. In another example, the user interface 129 communicatesan indication of one or more user 101 selections made via the userinterface 129.

An example account management system 130 comprises a server 131, awebsite 133, a data storage unit 135, an account management module 137,and a payment processing module 139.

In an example embodiment, the server 131 provides the content accessibleby the user 101 through the web browser 112 and/or digital walletapplication 117 resident on the user computing device 110, including butnot limited to html documents, images, style sheets, and scripts. In anexample embodiment, the server 151 supports the account managementsystem website 133.

In an example embodiment, the website 133 is a means by which the user101 establishes a digital wallet account with the account managementsystem 130. In an example embodiment, the user 101 adds, edits, ordeletes payment account information from a digital wallet accountassociated with the account management system 130 via the website 133.In an example embodiment, the user 101 accesses the website 133 via theweb browser 112. In another example embodiment, the user 101 accessesthe website 133 via digital wallet application 117 resident on the usercomputing device 110.

In an example embodiment, the data storage unit 135 comprises a local orremote data storage structure accessible to the payment card device 120suitable for storing information. In an example embodiment, the datastorage unit 123 stores encrypted information, such as HTML5 localstorage. In an example embodiment, the data storage unit 123 resideswithin a secure element 124. In an example embodiment, the data storageunit 135 stores information associated with a user's 101 digital walletaccount. For example, the data storage unit 135 may store paymentaccount information, user 101 identification information, or user 101verification information associated with the user's 101 digital walletaccount.

In an example embodiment, the account management module 137 receivespayment account information from the user computing device 110 that theuser 101 desires to enter into the user's 101 digital wallet account. Inan example embodiment, the account management module 137 may savereceived payment account information in the data storage unit 135. In anexample embodiment, the account management system 137 may edit or deleteexisting payment account information from the user's 101 digital walletaccount in response to receiving user 101 instructions from the digitalwallet application 117 or user computing device 110 to edit or deletepayment account information.

In an example embodiment, the payment processing module 139 receives arequest from the POS terminal 123 for payment account information to usein a user 101 initiated transaction. In an example embodiment, thepayment processing module 139 receives user 101 identificationinformation from the POS terminal 123. In an example embodiment, thepayment processing module 139 and/or the account management module 137identify the user's 101 digital wallet account based on the receiveduser 101 identification information. In an example embodiment, thepayment processing module 139 requests user 101 verification informationfrom the POS terminal 123. In an example embodiment, the paymentprocessing module 139 receives user 101 verification information fromthe POS terminal 123. In an example embodiment, the payment processingmodule 139 and/or account management module 137 verifies the validity ofthe user 101 verification information.

In an example embodiment, the payment processing module 139 transmits,to the POS terminal 123, one or more payment account information optionsto the POS terminal 123 for display to the user 101. In this exampleembodiment, the payment processing module 139 may obfuscate, occlude, ordelete portions of individual payment account information to producecorresponding individual payment account information options. In anexample embodiment, the payment processing module 139 receives anindication of a user 101 selection of one or more payment accountinformation options from the POS terminal 123. In an example embodiment,the payment processing module 139 generates, for each received selectionof a payment account information option, a payment token that may beused by the POS terminal 123 to process a transaction with anappropriate issuer system 150. In an example embodiment, the paymentprocessing module transmits the one or more generated payment tokens tothe POS terminal 123.

In an example embodiment, an acquirer system 140 may communicate with anissuer system 150 to approve a credit authorization and to make paymentto the merchant system 120. For example, the acquirer is a third partypayment processing company.

An example issuer system 150 is the issuer of payment accountinformation associated with a user's 101 digital wallet account. Forexample, the issuer system 150 may be a credit card issuer, a couponissuer, a voucher issuer, a bank account issuer, a merchant system 120account issuer, or other account issuer. In an example embodiment, thePOS terminal 123 communicates with one or more issuer systems 150 toprocess a user initiated transaction using one or more correspondingpayment tokens generated by the account management system 130. In anexample embodiment, the issuer system 150 receives the payment token anda payment authorization request. In an example embodiment, the issuersystem 150 identifies a payment account based on the payment token andapproves or declines the payment authorization request. In an exampleembodiment, the issuer system 150 communicates a notice of approval ordenial of the payment authorization request to the POS terminal 123.

It will be appreciated that the network connections shown are exampleand other means of establishing a communications link between thecomputers and devices can be used. Moreover, those having ordinary skillin the art having the benefit of the present disclosure will appreciatethat the user computing device 110, the merchant system 120, the accountmanagement system 130, the acquirer system 140, and the issuer system150 illustrated in FIG. 1 can have any of several other suitablecomputer system configurations. For example, a user computing device 110embodied as a mobile phone or handheld computer may or may not includeall the components described above.

In example embodiments, the network computing devices and any othercomputing machines associated with the technology presented herein maybe any type of computing machine such as, but not limited to, thosediscussed in more detail with respect to FIG. 11. Furthermore, anymodules associated with any of these computing machines, such as modulesdescribed herein or any other modules (scripts, web content, software,firmware, or hardware) associated with the technology presented hereinmay by any of the modules discussed in more detail with respect to FIG.9. The computing machines discussed herein may communicate with oneanother as well as other computer machines or communication systems overone or more networks, such as network 160. The network 160 may includeany type of data or communications network, including any of the networktechnology discussed with respect to FIG. 9.

Example Processes

The example methods illustrated in FIGS. 2-8 are described hereinafterwith respect to the components of the example operating environment 100.The example methods of FIGS. 2-8 may also be performed with othersystems and in other environments.

FIG. 2 is a block diagram depicting a method 200 for providing digitalwallet payment account information directly to a merchant system POSterminal 123 for user 101 selection, in accordance with certain exampleembodiments. The method 200 is described with reference to thecomponents illustrated in FIG. 1.

In block 210, a user 101 registers for a digital wallet account with anaccount management system 130.

FIG. 3 is a block diagram depicting a method 210 for registering for adigital wallet account with an account management system 130, inaccordance with certain example embodiments. The method 210 is describedwith reference to the components illustrated in FIG. 1.

In block 310, the user 101 accesses an account management system website133. In an example embodiment, the user 101 accesses the accountmanagement system website 133 via the web browser 112 of the usercomputing device 110. For example, the user 101 enters the website 133address in the address bar of the web browser 112 to access the website133. In another example embodiment, the user 101 accesses the accountmanagement system website 133 using an application resident on the usercomputing device 110. For example, the user 101 selects an applicationon the user computing device 110 that connects the user 101 to theaccount management system website 133.

In block 320, the user 101 establishes a digital wallet account. In anexample embodiment, the user 101 registers a username and a passwordassociated with the user account to use to sign in to the user 101digital wallet account. In an example embodiment, the user provides oneor more user 101 identification information to the account managementsystem 130 to associate with the digital wallet account. For example,the user 101 may provide a telephone number, an email address, aphysical address, and/or other user 101 identification information. Inan example embodiment, the account management system 130 associates theuser 101 identification information with the user's 101 digital walletaccount. In an example embodiment, the user 101 digital wallet accountis associated with one or more services, such as an email service, amessaging service, a gaming service, or a mapping service, provided bythe account management system 130.

In an example embodiment, when establishing the digital wallet accountwith the website 133, the user 101 provides user 101 verificationinformation to the account management system 130. In this exampleembodiment, the account management system 130 associates the user 101verification information with the user 101 digital wallet account.Example user 101 verification information comprises a password, apersonal identification number (“PIN”), or a selection of a particularimage from a plurality of images. In another example, verificationinformation comprises user 101 biometric information, such as afingerprint of the user 101, a retinal scan of the user 101, or a voicerecording of the user 101. In an example embodiment, the accountmanagement system 130 saves the user 101 verification information in thedata storage unit 135 and associates the user 101 verificationinformation with the user 101 digital wallet account. In this exampleembodiment, the account management system 130 may verify the user's 101identity by comparing received user 101 verification information to thesaved user 101 verification information.

In block 330, a digital wallet application 117 is downloaded onto theuser computing device 110. In an example embodiment, the digital walletapplication 117 communicates with the account management system 130 overthe network 160. In this example, the digital wallet payment application113 communicates with the account management system 130, whichadministers the user 101 digital wallet account. In another exampleembodiment, the user 101 may download various applications associatedwith the user account from the payment processing system 120 in additionto the digital wallet application 117. For example, the user 101downloads one or more of an email application, a mapping application, asocial network application, or a search application associated with theaccount management system 130. In this example, the user 101 maymaintain a universal username and/or password to access all theapplications associated with the account management system 130. Inanother example embodiment, the digital wallet application 117 isdownloaded onto the user computing device 110 before the user 101establishes the user 101 digital wallet account with the accountmanagement system 130. In certain example embodiments, the user 101 doesnot download the digital wallet application 117 onto the user computingdevice 110. For example, the user 101 may access the digital walletaccount using a web browser 112 application associated with the accountmanagement system 130 or may access the digital wallet account directlyon the account management system website 133 using the web browser 112.

In block 340, the user 101 transmits payment account information toenter into the digital wallet account via the digital wallet application117. In an example embodiment, the digital wallet application 117communicates with the account management system 130. In another exampleembodiment, the user 101 enters the payment account information usingthe via the web browser 112, which communicates with the accountmanagement system 130. In an example embodiment, the payment accountinformation entered by the user 101 is associated with one or more of acredit account, a debit account, a bank account, a coupon, a voucher, arewards points account, a merchant system 120 account, or other accountof the user 101, merchant system 120, or third party. In an exampleembodiment, each payment account is associated with a respective issuersystem 150. For example, the credit account is associated with a creditcard issuer system 150, the debit account and bank account areassociated with a financial institution issuer system 150, the coupon isassociated with a coupon issuer system 150, the rewards points accountis associated with a rewards points account issuer system 150, and themerchant system 120 account is associated with the merchant system 120acting as an issuer system 150. In an example embodiment, a creditaccount is associated with an issuer system 130 and an acquirer system140.

In an example embodiment, payment account information for a respectivebank account comprises an account number, a routing number, the nameassociated with the payment account, the address associated with thepayment account and/or any other relevant, useful, or necessaryinformation that the user 101 may enter into the user 101 digital walletaccount or that the user digital wallet account may require or requestfrom the user 101. In an example embodiment, the payment accountinformation associated with a credit account or a debit accountcomprises a credit card or debit card number, an expiration date, a cardverification number, the name associated with the credit account, and/orany other relevant, useful, or necessary information that the user 101may enter into the user account or that the user 101 digital walletaccount may require. In an example embodiment, the payment accountinformation associated with a coupon comprises a coupon number, abarcode or QR code, an expiration date, a coupon issuer system 150 name,a product name, a redemption condition, and/or any other relevant,useful, or necessary information that the user 101 may enter into theuser account or that the user 101 digital wallet account may require.

In certain example embodiments, to enter payment account information tothe user 101 digital wallet account, the user may scan or captureimages, using the user computing device 110 one or more paymentinstruments associated with one or more payment accounts and transmitthe images and/or scans to the account management system. In theseexample embodiments, the account management system 130 receives thescans and/or images of the payment instruments and determines thepayment information based on the scans and/or images. For example, theuser 101 captures an image of a barcode of a coupon via a camera moduleon the user computing device 110 and transmits the image to the accountmanagement system 130 for entry into the user 101 digital walletaccount. In this example, the account management system 130 receives theimage of the barcode of the coupon from the user computing device 110for entry into the user 101 digital wallet account. In this example, theaccount management system 130 determines the payment informationassociated with the coupon by interpreting the barcode in the receivedimage.

In an example embodiment, the account management system 130 receives thepayment account information of the user 101.

In block 350, the account management system 130 saves the user's paymentaccount information in the digital wallet account associated with theuser 101. In an example embodiment, the account management system 130saves the user's payment account information in a database, table, orother record that correlates the user 101 identification informationwith the user 101 verification information and the payment accountinformation associated with one or more payment accounts. In an exampleembodiment, the user 101 may access the digital wallet account via thedigital wallet application 117 and/or web browser 112 to add, edit,and/or delete payment account information.

From block 350, the method 210 proceeds to block 220 of FIG. 2.

Returning to FIG. 2, in block 220, the user 101 initiates a digitalwallet transaction at a POS terminal 123 of the merchant system 120.

FIG. 4 is a block diagram depicting a method 220 for initiating, by auser 101, a transaction at a merchant system point of sale terminal 123,in accordance with certain example embodiments. The method 220 isdescribed with reference to the components illustrated in FIG. 1.

In block 410, the user 101 enters a merchant system 120 location. Forexample, a merchant system 120 comprises one or more physical locationsat one or more respective physical street addresses.

In block 420, the user 101 selects one or more items for sale. Forexample, the user 101 enters the merchant system 120 location andselects one or more items from the merchant system 120 location's storeshelves for purchase.

In block 430, the user 101 approaches a merchant system POS terminal 123to check out. In an example embodiment, the POS terminal 123 is aself-checkout terminal. In another example embodiment, the POS terminal123 is operated by an agent of the merchant system 120. In an exampleembodiment, the user 101 or the agent of the merchant system 120 scansand/or enters information associated with the one or more items into thePOS terminal 123. For example, an agent of the merchant system 120 scansbarcodes of all the user's 101 selected items using a barcode scanner ofthe POS terminal 123. In example embodiment, the POS terminal 123calculates a total cost of transaction to purchase the one or more itemsand displays the total to the user 101 via the user interface 129.

In block 440, the POS terminal 123 presents the user 101 with one ormore payment options comprising an option to check out using a digitalwallet account. For example, the POS terminal 123 displays paymentoptions comprising options for the user 101 to pay using cash, check,credit card, debit card, money order, coupon, merchant system 120 storecredit account, rewards card, or other acceptable method of payment inaddition to an option to check out using a digital wallet account. In anexample embodiment, the POS terminal 123 displays, on the user interface129, the one or more payment options represented by one or more objectson the user interface 129 selectable by the user 101. In an exampleembodiment, the POS terminal 123 displays an option to check out using adigital wallet account associated with a particular account managementsystem 130. In another example embodiment, the POS terminal 123 displaysone or more options to check out with one or more digital walletaccounts associated with one or more respective account managementsystems 130. For example, the POS terminal 123 displays a first optionto check out using a digital wallet account associated with accountmanagement system A and a second option to check out using a digitalwallet account associated with account management system B.

In block 450, the user 101 selects an option to check out using adigital wallet account. For example, the user 101 selects an object onthe user interface 129 of the POS terminal 123 representing the optionto check out using the digital wallet account. In another example, theuser 101 directs an agent of the merchant system 120 operating the POSterminal 123 to select an option to check out using the digital walletaccount.

In block 460, the POS terminal 123 displays a request for user 101identification information to the user 101. In an example embodiment,the POS terminal 123 displays the request for user 101 identificationinformation on the user interface 129. In an example embodiment, the POSterminal 123 is configured by the merchant system 120 and or the accountmanagement system 130 associated with the user's 101 digital walletaccount to request user 101 identification information in response toreceiving a selection from the user 101 of the option to check out usinga digital wallet account. In another example embodiment, the POSterminal 123 communicates an indication to the account management system130 of the user 101 selection of an option to check out using a digitalwallet. In this example embodiment, the account management system 130transmits a request for user 101 identification information, which thePOS terminal 123 displays to the user 101 on the user interface 129.

In block 470, the user 101 enters user 101 identification informationvia the user interface 129 of the POS terminal 123. In an exampleembodiment, the user interface 129 comprises a touch screen interfaceand comprises a touch screen keyboard comprising alphanumeric charactersand/or symbols that the user 101 may input by touching the screen. Forexample, the user 101 enters a username, telephone number, address,email address, and/or other user 101 identification informationassociated with the digital wallet account via the user interface 129.In another example embodiment, the user interface 129 comprises afingerprint scanner, retinal scanner, or voice recorder wherein the user101 submits user 101 identification information comprising afingerprint, retinal scan, or voice recording to the POS terminal 123.

In certain other example embodiments, the user 101 identificationinformation comprises a hardware identifier associated with a usercomputing device 110 in the user's 101 possession at the time oftransaction. In an example embodiment, at a time after a user 101selects an option to check out using a digital wallet account, themerchant POS terminal 123 establishes a wireless communication channelwith a user computing device 110 of the user 110. For example, thewireless communication channel comprises a Bluetooth communicationchannel, a near field communication (“NFC”) channel, or a Wi-Ficommunication channel. For example, the user computing device 110 andthe merchant POS terminal 123 periodically or continuously emit proberequests using a respective wireless communication protocol. In thisexample, a first device, either the user computing device 110 or themerchant POS terminal 123, detects the presence of the other device in aphysical proximity conforming to the communication protocol. In thisexample, the first device transmits a request to establish a wirelesscommunication channel to the other device, the other device receives therequest, the other device transmits a confirmation response back to thefirst device, establishing a wireless communication channel. In thisexample embodiment, the user 101 operating the user computing device 110must select an option on the user interface 119 to allow the wirelesscommunication channel to be established. For example, the user 101 viewsa request on the user computing device 110 that says “do you wish toestablish a wireless connection with Merchant A?” and selects an objecton the user interface 119 that says “yes, I wish to establish a wirelessconnection with Merchant A.” In an example embodiment, afterestablishing a wireless communication channel, the user computing device110 and POS terminal 123 may exchange cryptographic keys to enablecryptographic communication via a secure wireless communication channel.In an example embodiment, the POS terminal 123 transmits a request tothe user computing device 110, via the wireless communication channel,for a user computing device 110 hardware identifier. In this exampleembodiment, the user computing device 110 transmits the hardwareidentifier to the POS terminal 123 in response to receiving the request.An example hardware identifier comprises a MAC address, a serial number,or other identifier associated with the user computing device 110.

From block 470, the method 220 proceeds to block 230 in FIG. 2.

Returning to FIG. 2, in block 230, the user 101 verifies his identity atthe POS terminal 123. In other example embodiments, the user 101 is notrequired to verify his or her identify in a separate step because theuser 101 identification information transmitted by the user 101 to themerchant system POS terminal 123 comprises or further comprises user 101verification information.

FIG. 5 is a block diagram depicting a method 230 for providing user 101identification information and user 101 verification information at apoint of sale terminal 123 for verification by an account managementsystem 130, in accordance with certain example embodiments. The method230 is described with reference to the components illustrated in FIG. 1.

In block 510, the POS terminal 123 transmits a payment informationrequest and the user 101 identification information to the accountmanagement system 130. For example, the POS terminal 123 transmits theuser 101 identification information received from the user 101 at theuser interface 129 to the account management system 130.

In block 520, the account management system 130 receives the paymentinformation request and the user 101 identification information.

In block 530, the account management system 130 identifies and accessesthe digital wallet account of the user 101 using the received user 101identification information. In an example embodiment, the accountmanagement system 130 comprises a database or table that correlates user101 identification information with respective digital wallet accountidentifiers. In this example embodiment, the account management system130 accesses the table or database, finds the entry corresponding to thereceived user 101 identification information, and identifies the digitalwallet account of the user 101 associated with the user 101identification information. For example, the account management system130 receives a telephone number associated with the user's 101 digitalwallet account and identifies the digital wallet account by looking upthe telephone number in the table or database. In example embodiment,the user 101 identification information entered by the user 101 andreceived from the POS terminal 123 is identical to the user 101identification information that the user 101 provided to the accountmanagement system 130 when establishing the digital wallet account. Inthis example embodiment, the account management system 130 should beable to identify the user's 101 digital wallet account based on thereceived user 101 identification information. In other exampleembodiments, the user 101 submits invalid or incorrect identificationfor which the account management system 130 is unable to find acorresponding digital wallet account via the table or database. In theseexample embodiments, the account management system 130 may transmit anotice to the POS terminal 123 that the user 101 identificationinformation submitted by the user 101 is incorrect and a request forsecond user 101 identification information. The POS terminal 123 maydisplay the notice of incorrect user 101 identification information andmay display the request for second user 101 identification information.The user 101 may then enter second user 101 identification informationthat the POS terminal 123 may transmit to the account management system130. In this example embodiment, the account management system 130identifies the digital wallet account of the user 101 based on thesecond user 101 identification information.

In block 540, the POS terminal 123 provides, to the account managementsystem 130, user 101 verification information entered by the user 101 atthe POS terminal 123 user interface 129. In other example embodiments,the user 101 identification information comprises user 101 verificationinformation and the user 101 does not have to separately submitverification information. For example, a user 101 fingerprint scan maycomprise both user 101 identification information and user 101verification information. In another example, the user 101 provides theuser 101 verification information at the same time that the user 101provides the user 101 identification information. In another exampleembodiment, the user 101 does not provide verification information tothe POS terminal 123.

FIG. 6 is a block diagram depicting a method 540 for providing user 101verification information received at a POS terminal 123 to an accountmanagement system 130, in accordance with certain example embodiments.The method 540 is described with reference to the components illustratedin FIG. 1.

In block 610, the account management system 130 transmits a request foruser 101 verification information to the POS terminal 123. In an exampleembodiment, the POS terminal 123 is configured to accept a certain typeof user 101 verification information. For example, the POS terminal userinterface 129 comprises a fingerprint scanner, a touch screen keyboard,an external keyboard, or other applicable user interface 129 thatenables a user 101 to enter user 101 verification information.

In block 620, the POS terminal 123 receives the request for user 101verification information and displays the request to the user 101 viathe user interface 129. For example, the POS terminal 123 displays amessage that reads, “Please provide your digital wallet account passwordusing the keyboard.”

In block 630, the user 101 inputs user 101 verification information tothe POS terminal 123 via the user interface 129. For example, the user101 enters a password, enters a PIN, selects an image from among aplurality of displayed images, undergoes a fingerprint scan, submits avoice recording, undergoes a retinal scan, or submits other appropriateuser 101 verification information. In another example embodiment, theuser 101 does not submit user 101 verification information to the POSterminal 123.

In block 640, the POS terminal 123 transmits the user 101 verificationinformation to the account management system 130. For example, the POSterminal 123 transmits the user 101 verification information via thenetwork 160 to the account management system 130. In an exampleembodiment, the account management system 130 receives the user 101verification information.

From block 640, the method 540 proceeds to block 550 in FIG. 5.

Returning to FIG. 5, in block 550, the account management system 130determines whether the received user 101 verification information isvalid. In an example embodiment, the account management system 130comprises a table or database that correlates user 101 verificationinformation to user 101 identification information and/or user digitalwallet account identifiers.

If the account management system 130 determines that the received user101 verification information is invalid, the method 230 returns to block540. In an example embodiment, the account management system 130identified the digital wallet account of the user 101 based on thereceived user 101 identification information. In this exampleembodiment, the account management system 130 locates an entry in thedatabase or table that correlates user 101 verification information touser 101 identification information and/or user digital wallet accountidentifiers. In this example embodiment, the account management system130 compares the received user verification identification against theuser 101 verification information associated with the user 101identification information in the database or table. In this exampleembodiment, the account management system 130 determines that thereceived user 101 verification information is invalid if the receiveduser 101 verification information does not match, exactly or within apredetermined margin of error, the user 101 verification informationassociated with the user's digital wallet account identifier and useridentifying information stored in the table. For example, received user101 verification information comprising a user 101 fingerprint scan isonly 30% similar to a fingerprint scan associated with the user 101digital wallet account. In this example, the account management system130 requires that a received fingerprint scan have a 99% similarity tothe fingerprint scan associated with the user's 101 digital walletaccount to be considered valid user 101 verification information. Inthis example, the account management system 130 determines that thereceived user 101 verification information comprising the fingerprintscan is invalid user 101 verification information because the 30%similarity is below the required 99% threshold.

In block 540, the POS terminal 123 provides, to the account managementsystem 130, user 101 verification information entered by the user 101 atthe POS terminal 123. For example, the account management system 130notifies the POS terminal 123 that the first user 101 verificationinformation entered by the user is invalid. In this example, the POSterminal 123 displays a request for the user to re-enter user 101verification information. In this example embodiment, the user 101enters second user 101 verification information into the POS terminal123, which communicates the second user 101 verification information tothe account management system 130. In this example, the accountmanagement system 130 determines the validity of the second user 101verification information according to the previously discussed method.

Returning to block 550, if the account management system 130 determinesthat the received user 101 verification information is valid, the method230 proceeds to block 560. In an example embodiment, the accountmanagement system 130 identified the digital wallet account of the user101 based on the received user 101 identification information. In thisexample embodiment, the account management system 130 locates an entryin the database or table that correlates user 101 verificationinformation to user 101 identification information and/or user digitalwallet account identifiers. In this example embodiment, the accountmanagement system 130 compares the received user verificationidentification against the user 101 verification information associatedwith the user 101 identification information in the database or table.In this example embodiment, the account management system 130 determinesthat the received user 101 verification information is valid if thereceived user 101 verification information matches, exactly or within apredetermined margin of error, the user 101 verification informationassociated with the user's digital wallet account identifier and useridentifying information stored in the table. For example, the accountmanagement system 130 receives user 101 verification informationcomprising a password reading “george146!” and the user 101 verificationinformation associated with the user's 101 digital wallet account anduser 101 identification information in the table comprises a passwordreading “george146!” In this example, the account management system 130determines that the received user 101 verification information is validbecause the received password exactly matches the password associatedwith the user's 101 digital wallet account.

In block 560, the account management system 130 transmits paymentaccount information options associated with the user 101 digital walletaccount to the POS terminal 123. In an example embodiment, each paymentinformation option corresponds to respective payment account informationsubmitted by the user 101 to the digital wallet account. In an exampleembodiment, the account management system 130 may not transmit paymentinformation options comprising complete payment information associatedwith respective payment accounts. For example, the account managementsystem 130 may abbreviate, obfuscate, or occlude one or more parts ofthe payment account information associated with each payment option. Forexample, payment account information associated with a credit card maycomprise “Issuer A credit card, 4565-9878-4855-1429, expiration date11/13/17.” In this example, the payment account information optiontransmitted by the account management system 130 to the POS terminal 123may comprise “Issuer A credit card, xxxx-xxxx-xxxx-1429, expiration date11/13/17.” In this example, the account management system 130 hasdeleted the first twelve digits and represented them by an “x” in thepayment account information option. In other example embodiments, theaccount management system 130 transmits payment account informationoptions comprising payment account information for each payment accountinformation option in its entirety.

From block 560, the method 230 proceeds to block 240 in FIG. 2.

Returning to FIG. 2, in block 240, the POS terminal 123 receives thepayment account information options associated with the user 101 digitalwallet account from the account management system 130.

In block 250, the user 101 selects a payment account information optionassociated with the user 101 digital wallet account via the POS terminal123 user interface 129.

FIG. 7 is a block diagram depicting a method 250 for selecting a paymentaccount information option associated with a user 101 digital walletaccount via a POS terminal 123 user interface 129, in accordance withcertain example embodiments. The method 540 is described with referenceto the components illustrated in FIG. 1.

In block 710, the POS terminal 123 displays received payment accountinformation options to the user 101. In an example embodiment, the POSterminal 123 displays one or more icons on the user interface 129 of thePOS terminal 123, each icon corresponding to one of one or more receivedpayment account information options. In an example embodiment, thepayment account information options do not display complete paymentaccount information. For example, payment account information for acredit card account comprises “Issuer A credit card,9885-3440-0034-2906, expiration date—01/14/18.” In this example, thedisplayed payment account information option corresponding to thepayment account information may comprise “xxxx-xxxx-xxxx-2906,expiration date—01/14/18.” In this example, the first twelve digits ofthe credit card number are not displayed to the user 101.

In block 720, the user 101 selects a payment account information optionvia the POS terminal 123 user interface 129. In an example embodiment,the user 101 actuates one or more objects on the user interface 129 ofthe POS terminal 123 to select a particular payment account informationoption. In another example embodiment, the user 101 selects two or morepayment account information options via the user interface 129. Forexample, the user selects both a credit card and a coupon from among thedisplayed payment account information options to apply to thetransaction.

In block 730, the POS terminal 123 communicates an indication of theuser 101 selection of the payment account information option to theaccount management system 130. For example, the POS terminal 123transmits the indication of the user 101 selection of the paymentaccount information option comprising “Issuer A credit card,xxxx-xxxx-xxxx-2906, expiration date—01/14/18” over the network 160 tothe account management system 130. In another example embodiment, thePOS terminal 123 communicates an indication of the user 101 selection oftwo or more payment account information options to the accountmanagement system 130.

In block 740, the account management system 130 receives the indicationof the user 101 selection of the payment account information option. Inanother example embodiment, the account management system 130 receivesan indication of the user 101 selection of two or more payment accountinformation options. In an example embodiment, for each particularselected payment account information option, the account managementsystem 130 identifies corresponding payment account information. In anexample embodiment, the account management system 130 comprises a tableor database that correlates payment account information options tocorresponding payment account information associated with a user's 101digital wallet account. For example, a user 101 selected a paymentaccount information option “Issuer A credit card, xxxx-xxxx-xxxx-2906,expiration date—01/14/18” that corresponds to payment accountinformation comprising “Issuer A credit card, 9885-3440-0034-2906,expiration date—01/14/18.” In this example, the account managementsystem 130 receives the selection of the payment account informationoption, finds the payment account information option in the table ordatabase, and identifies the payment account information associated inthe table or database with the payment account information option.

In block 750, the account management system 130 generates a paymenttoken based on the payment account information associated with theuser-selected payment account information option. In an exampleembodiment, a payment token comprises information to be used by the POSterminal 123 necessary to process a transaction with an issuer system150 associated with the payment account information. For example, theissuer system 150 may comprise a credit card issuer system 150, abanking institution issuer system 150, a coupon issuer system 150, arewards card issuer system 150, or a merchant system 130. In an exampleembodiment, the payment token comprises part or all of the paymentaccount information associated with the payment account informationoption selected by the user 101 via the POS terminal user interface 129for use in the transaction. For example, the payment token may comprisea credit card number, an expiration date, and/or any other relevantpayment information necessary to process a transaction. In anotherexample, the payment token may comprise the same data that would beprovided to a merchant system POS terminal 123 by a user if the userphysically swiped or scanned a payment instrument associated with thepayment account information option. In another example embodiment, theissuer system 150 stores complete payment account information for apayment account information option selected by the user 101. In thisexample embodiment, the payment token comprises data that can becorrelated by the issuer system 150 to the payment account informationstored by the issuer system 150. For example, the payment token maycomprise a virtual credit number that, when received from the merchantsystem POS terminal 123, can be used by the issuer system 150 toidentify a credit card account of the user 101. In another exampleembodiment, the account management system 130 generates two or morepayment tokens corresponding to two or more respective payment accountinformation options selected by the user 101 at the merchant system POSterminal user interface 129.

In block 760, the account management system 130 transmits the paymenttoken to the POS terminal 123. For example, the account managementsystem 130 transmits the payment token via the network 160 to themerchant system POS terminal 123. In another example embodiment, theaccount management system 130 transmits two or more payment tokens tothe POS terminal 123.

From block 760, the method 250 proceeds to block 260 in FIG. 2.

Returning to FIG. 2, in block 260, the POS system receives a paymenttoken from the account management system 130.

In block 270, the POS terminal 123 communicates with the issuer system150 to process the transaction using the payment token. For example, theissuer system 150 may comprise a credit card issuer system 150, a bankissuer system 150, a coupon issuer system 150, or a merchant system 120issuer system 150. In another example embodiment, the POS terminal 123communicates with two or more issuer systems 150 to process thetransaction using two or more payment tokens. For example, the POSterminal 123 communicates with a coupon issuer system 150 to process afirst transaction using a first payment token comprising coupon paymentaccount information and communicates with a credit card issuer system150 to process a second transaction using a second payment tokencomprising credit card account information.

FIG. 8 is a block diagram depicting a method 270 for communicating withan issuer system 150 to process a transaction using a payment token, inaccordance with certain example embodiments. The method 270 is describedwith reference to the components illustrated in FIG. 1. In certainexample embodiments, the POS terminal 123 communicates separately witheach of two or more issuer systems 150 to process two or moretransactions using two or more respective payment tokens.

In block 810, the POS terminal 123 transmits the payment token and apayment authorization request to the issuer system 150. For example, thePOS terminal 123 transmits the payment token and the paymentauthorization request via the network 160 to the issuer system 150. Inan example embodiment, the payment authorization request comprises atransaction total, merchant system 120 payment account information,and/or other useful information used to process a payment transaction orreimburse the merchant system 120. In an example embodiment, the paymenttoken comprises payment account information associated with a paymentaccount of the user.

In block 820, the issuer system 150 receives the payment token and thepayment authorization request.

In block 830, the issuer system 150 identifies a payment accountassociated with the payment token. In an example embodiment, the issuersystem 150 extracts payment account information from the payment token.In another example embodiment, the issuer system 150 comprises a tableor database that correlates payment tokens to corresponding paymentaccounts. In this example embodiment, the issuer system 150 searches forthe payment token in the table or the database and identifies a paymentaccount associated with the payment token using the table or database.For example, the payment token comprises a coupon code, the issuersystem 150 is a coupon issuer system 150, and the coupon issuer system150 comprises a table that correlates coupon codes to coupon accounts ofthe coupon issuer system 150. In this example, the coupon issuer system150 searches for the coupon code in the table and identifies acorresponding coupon account of the coupon issuer system 150. In thisexample, this coupon account may be used to reimburse a merchant system120 for the value of a coupon issuer system 150 coupon used in atransaction. In another example, the payment token comprises a creditcard account number and the issuer system 150 is a credit card issuersystem 150. In this example, the issuer system 150 identifies the user101 payment account based on the received credit card account number. Inyet another example, the payment token comprises a virtual credit cardnumber. In this example, the issuer system 150 comprises a table thatcorrelates virtual credit card numbers to user 101 credit paymentaccounts. In this example, the issuer system 150 may generate thevirtual credit number for the user 101 to use instead of the true creditaccount number.

In block 840, the issuer system 150 determines whether to approve or todecline the payment transaction. In an example embodiment, a credit cardissuer system 150 determines whether to approve or decline the paymenttransaction based on the user's 101 current balance, the user's 101credit limit, and/or the amount of the current transaction. In anotherexample embodiment, a coupon issuer system 150 determines whether toapprove or decline the payment transaction based on the conditionsimposed by a coupon being used in the transaction and transaction datareceived from the merchant system POS terminal 123.

If the issuer system 150 approves the payment transaction, the method270 proceeds to block 860. For example, a credit card issuer system 150approves the payment transaction because the user 101 credit limit andcurrent credit balance are such that the current transaction amount willnot cause the user's 101 credit balance to exceed the credit limit. Inanother example, a coupon issuer system 150 approves the paymenttransaction based on the data received from the merchant system POSterminal 123. In this example, the coupon issuer system 150 determinesthat the user 101 satisfies the coupon terms and conditions based on thedata received from the merchant system POS terminal 123.

In block 860, the issuer system 150 transmits a notice of authorizedpayment transaction to the POS terminal 123. An example notice ofauthorized payment transaction may comprise a transaction number, aconfirmation number, a transaction amount, a portion of the user accountnumber used in the transaction, a time of transaction, and/or any otheruseful or relevant information to the transaction. In an exampleembodiment, the POS terminal 123 receives the notice of authorizedpayment transaction.

In block 870, the POS terminal 123 processes the transaction andgenerates a transaction receipt. In an example embodiment, the POSterminal 123 prints a paper transaction receipt at the POS terminal 123via a printer resident on the POS terminal 123. In another exampleembodiment, the POS terminal 123 and/or the merchant system 120transmits an electronic receipt to the user computing device 110 viaemail, text messaging, or other appropriate means. In an exampleembodiment, the transaction receipt communicates to the user 101 thetransaction total and that the transaction was approved by the issuersystem 150. In an example embodiment, the transaction receipt comprisesa merchant system 120 name, an address of the physical location of themerchant system 120 at which the user 101 made the purchase, atransaction amount, a portion of the payment account number used in thetransaction, the date of transaction, descriptions and/or prices of oneor more items purchased in the transaction, and/or any other useful orrelevant information associated with the transaction.

Returning to block 840, if the issuer system 150 declines the paymenttransaction, the method 270 proceeds to block 850. For example, a creditcard issuer system 150 declines the payment transaction because the user101 credit limit and current credit balance are such that the currenttransaction amount would cause the user's 101 credit balance to exceedthe credit limit. In another example, a coupon issuer system 150declines the payment transaction based on the data received from themerchant system POS terminal 123. In this example, the coupon issuersystem 150 determines that the user 101 satisfies the coupon terms andconditions based on the data received from the merchant system POSterminal 123.

In block 850, the POS terminal 123 receives notice of a declined paymenttransaction. In an example embodiment, the issuer system 150 transmitsthe notice of a declined payment transaction to the POS terminal 123. Anexample notice of approved payment transaction may comprise atransaction number, a transaction amount, a portion of the user accountnumber used in the transaction, a time of transaction, and/or any otheruseful or relevant information to the transaction.

In block 880, the POS terminal 123 generates a transaction receipt. Inan example embodiment, the POS terminal 123 prints a paper transactionreceipt at the POS terminal 123 via a printer resident on the POSterminal 123. In another example embodiment, the POS terminal 123 and/orthe merchant system 120 transmits an electronic receipt to the usercomputing device 110 via email, text messaging, or other appropriatemeans. In an example embodiment, the transaction receipt communicates tothe user 101 the transaction total and that the transaction was declinedby the issuer system 150. In an example embodiment, the transactionreceipt comprises a merchant system 120 name, an address of the physicallocation of the merchant system 120 at which the user 101 attempted tomake the purchase, a transaction amount, a portion of the paymentaccount number used in the attempted transaction, the date of theattempted transaction, descriptions and/or prices of one or more itemsthat were intended to be purchased in the attempted transaction, and/orany other useful or relevant information associated with the declinedtransaction.

From block 880, the method 270 proceeds to block 280 in FIG. 2.

Returning to FIG. 2, in block 280, the user 101 receives the transactionreceipt. For example, the POS terminal 123 prints the transactionreceipt and the user 101 receives the receipt at the POS terminal 123.In another example, the POS terminal 123 sends an email or text messageto the user 101 comprising the transaction receipt, which the userreceives via the user computing device.

Other Example Embodiments

FIG. 9 depicts a computing machine 2000 and a module 2050 in accordancewith certain example embodiments. The computing machine 2000 maycorrespond to any of the various computers, servers, mobile devices,embedded systems, or computing systems presented herein. The module 2050may comprise one or more hardware or software elements configured tofacilitate the computing machine 2000 in performing the various methodsand processing functions presented herein. The computing machine 2000may include various internal or attached components such as a processor2010, system bus 2020, system memory 2030, storage media 2040,input/output interface 2060, and a network interface 2070 forcommunicating with a network 2080.

The computing machine 2000 may be implemented as a conventional computersystem, an embedded controller, a laptop, a server, a mobile device, asmartphone, a set-top box, a kiosk, a vehicular information system, onemore processors associated with a television, a customized machine, anyother hardware platform, or any combination or multiplicity thereof. Thecomputing machine 2000 may be a distributed system configured tofunction using multiple computing machines interconnected via a datanetwork or bus system.

The processor 2010 may be configured to execute code or instructions toperform the operations and functionality described herein, managerequest flow and address mappings, and to perform calculations andgenerate commands. The processor 2010 may be configured to monitor andcontrol the operation of the components in the computing machine 2000.The processor 2010 may be a general purpose processor, a processor core,a multiprocessor, a reconfigurable processor, a microcontroller, adigital signal processor (“DSP”), an application specific integratedcircuit (“ASIC”), a graphics processing unit (“GPU”), a fieldprogrammable gate array (“FPGA”), a programmable logic device (“PLD”), acontroller, a state machine, gated logic, discrete hardware components,any other processing unit, or any combination or multiplicity thereof.The processor 2010 may be a single processing unit, multiple processingunits, a single processing core, multiple processing cores, specialpurpose processing cores, co-processors, or any combination thereof.According to certain embodiments, the processor 2010 along with othercomponents of the computing machine 2000 may be a virtualized computingmachine executing within one or more other computing machines.

The system memory 2030 may include non-volatile memories such asread-only memory (“ROM”), programmable read-only memory (“PROM”),erasable programmable read-only memory (“EPROM”), flash memory, or anyother device capable of storing program instructions or data with orwithout applied power. The system memory 2030 may also include volatilememories such as random access memory (“RAM”), static random accessmemory (“SRAM”), dynamic random access memory (“DRAM”), and synchronousdynamic random access memory (“SDRAM”). Other types of RAM also may beused to implement the system memory 2030. The system memory 2030 may beimplemented using a single memory module or multiple memory modules.While the system memory 2030 is depicted as being part of the computingmachine 2000, one skilled in the art will recognize that the systemmemory 2030 may be separate from the computing machine 2000 withoutdeparting from the scope of the subject technology. It should also beappreciated that the system memory 2030 may include, or operate inconjunction with, a non-volatile storage device such as the storagemedia 2040.

The storage media 2040 may include a hard disk, a floppy disk, a compactdisc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), aBlu-ray disc, a magnetic tape, a flash memory, other non-volatile memorydevice, a solid state drive (“SSD”), any magnetic storage device, anyoptical storage device, any electrical storage device, any semiconductorstorage device, any physical-based storage device, any other datastorage device, or any combination or multiplicity thereof. The storagemedia 2040 may store one or more operating systems, application programsand program modules such as module 2050, data, or any other information.The storage media 2040 may be part of, or connected to, the computingmachine 2000. The storage media 2040 may also be part of one or moreother computing machines that are in communication with the computingmachine 2000 such as servers, database servers, cloud storage, networkattached storage, and so forth.

The module 2050 may comprise one or more hardware or software elementsconfigured to facilitate the computing machine 2000 with performing thevarious methods and processing functions presented herein. The module2050 may include one or more sequences of instructions stored assoftware or firmware in association with the system memory 2030, thestorage media 2040, or both. The storage media 2040 may thereforerepresent examples of machine or computer readable media on whichinstructions or code may be stored for execution by the processor 2010.Machine or computer readable media may generally refer to any medium ormedia used to provide instructions to the processor 2010. Such machineor computer readable media associated with the module 2050 may comprisea computer software product. It should be appreciated that a computersoftware product comprising the module 2050 may also be associated withone or more processes or methods for delivering the module 2050 to thecomputing machine 2000 via the network 2080, any signal-bearing medium,or any other communication or delivery technology. The module 2050 mayalso comprise hardware circuits or information for configuring hardwarecircuits such as microcode or configuration information for an FPGA orother PLD.

The input/output (“I/O”) interface 2060 may be configured to couple toone or more external devices, to receive data from the one or moreexternal devices, and to send data to the one or more external devices.Such external devices along with the various internal devices may alsobe known as peripheral devices. The I/O interface 2060 may include bothelectrical and physical connections for operably coupling the variousperipheral devices to the computing machine 2000 or the processor 2010.The I/O interface 2060 may be configured to communicate data, addresses,and control signals between the peripheral devices, the computingmachine 2000, or the processor 2010. The I/O interface 2060 may beconfigured to implement any standard interface, such as small computersystem interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel,peripheral component interconnect (“PCI”), PCI express (PCIe), serialbus, parallel bus, advanced technology attached (“ATA”), serial ATA(“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, variousvideo buses, and the like. The I/O interface 2060 may be configured toimplement only one interface or bus technology. Alternatively, the I/Ointerface 2060 may be configured to implement multiple interfaces or bustechnologies. The I/O interface 2060 may be configured as part of, allof, or to operate in conjunction with, the system bus 2020. The I/Ointerface 2060 may include one or more buffers for bufferingtransmissions between one or more external devices, internal devices,the computing machine 2000, or the processor 2010.

The I/O interface 2060 may couple the computing machine 2000 to variousinput devices including mice, touch-screens, scanners, electronicdigitizers, sensors, receivers, touchpads, trackballs, cameras,microphones, keyboards, any other pointing devices, or any combinationsthereof. The I/O interface 2060 may couple the computing machine 2000 tovarious output devices including video displays, speakers, printers,projectors, tactile feedback devices, automation control, roboticcomponents, actuators, motors, fans, solenoids, valves, pumps,transmitters, signal emitters, lights, and so forth.

The computing machine 2000 may operate in a networked environment usinglogical connections through the network interface 2070 to one or moreother systems or computing machines across the network 2080. The network2080 may include wide area networks (WAN), local area networks (LAN),intranets, the Internet, wireless access networks, wired networks,mobile networks, telephone networks, optical networks, or combinationsthereof. The network 2080 may be packet switched, circuit switched, ofany topology, and may use any communication protocol. Communicationlinks within the network 2080 may involve various digital or an analogcommunication media such as fiber optic cables, free-space optics,waveguides, electrical conductors, wireless links, antennas,radio-frequency communications, and so forth.

The processor 2010 may be connected to the other elements of thecomputing machine 2000 or the various peripherals discussed hereinthrough the system bus 2020. It should be appreciated that the systembus 2020 may be within the processor 2010, outside the processor 2010,or both. According to some embodiments, any of the processor 2010, theother elements of the computing machine 2000, or the various peripheralsdiscussed herein may be integrated into a single device such as a systemon chip (“SOC”), system on package (“SOP”), or ASIC device.

In situations in which the systems discussed here collect personalinformation about users, or may make use of personal information, theusers may be provided with an opportunity or option to control whetherprograms or features collect user information (e.g., information about auser's social network, social actions or activities, profession, auser's preferences, or a user's current location), or to control whetherand/or how to receive content from the content server that may be morerelevant to the user. In addition, certain data may be treated in one ormore ways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over how information is collected about the userand used by a content server.

Embodiments may comprise a computer program that embodies the functionsdescribed and illustrated herein, wherein the computer program isimplemented in a computer system that comprises instructions stored in amachine-readable medium and a processor that executes the instructions.However, it should be apparent that there could be many different waysof implementing embodiments in computer programming, and the embodimentsshould not be construed as limited to any one set of computer programinstructions. Further, a skilled programmer would be able to write sucha computer program to implement an embodiment of the disclosedembodiments based on the appended flow charts and associated descriptionin the application text. Therefore, disclosure of a particular set ofprogram code instructions is not considered necessary for an adequateunderstanding of how to make and use embodiments. Further, those skilledin the art will appreciate that one or more aspects of embodimentsdescribed herein may be performed by hardware, software, or acombination thereof, as may be embodied in one or more computingsystems. Moreover, any reference to an act being performed by a computershould not be construed as being performed by a single computer as morethan one computer may perform the act.

The example embodiments described herein can be used with computerhardware and software that perform the methods and processing functionsdescribed herein. The systems, methods, and procedures described hereincan be embodied in a programmable computer, computer-executablesoftware, or digital circuitry. The software can be stored oncomputer-readable media. For example, computer-readable media caninclude a floppy disk, RAM, ROM, hard disk, removable media, flashmemory, memory stick, optical media, magneto-optical media, CD-ROM, etc.Digital circuitry can include integrated circuits, gate arrays, buildingblock logic, field programmable gate arrays (FPGA), etc.

The example systems, methods, and acts described in the embodimentspresented previously are illustrative, and, in alternative embodiments,certain acts can be performed in a different order, in parallel with oneanother, omitted entirely, and/or combined between different exampleembodiments, and/or certain additional acts can be performed, withoutdeparting from the scope and spirit of various embodiments. Accordingly,such alternative embodiments are included in the scope of the followingclaims, which are to be accorded the broadest interpretation so as toencompass such alternate embodiments.

Although specific embodiments have been described above in detail, thedescription is merely for purposes of illustration. It should beappreciated, therefore, that many aspects described above are notintended as required or essential elements unless explicitly statedotherwise. Modifications of, and equivalent components or actscorresponding to, the disclosed aspects of the example embodiments, inaddition to those described above, can be made by a person of ordinaryskill in the art, having the benefit of the present disclosure, withoutdeparting from the spirit and scope of embodiments defined in thefollowing claims, the scope of which is to be accorded the broadestinterpretation so as to encompass such modifications and equivalentstructures.

What is claimed is:
 1. A computer-implemented method to process atransaction via digital wallet payment account information of a user ata point of sale computing device of a merchant computing system,comprising: receiving, by one or more computing devices and from a pointof sale computing device associated with a merchant computing system,user identification information associated with a user and a request forpayment account information associated with a digital wallet account ofthe user; identifying, by the one or more computing devices, the digitalwallet account of the user based on the received user identificationinformation; retrieving, by the one or more computing devices, one ormore payment account options associated with the digital wallet accountof the user; transmitting, by the one or more computing devices and tothe point of sale computing device, the one or more payment accountoptions for presentation by the point of sale computing device;receiving, by the one or more computing devices and from the point ofsale computing device, an indication of a selection at the point of salecomputing device of a particular payment account option from the one ormore transmitted payment account options; generating, by the one or morecomputing devices, a payment token based on payment account informationassociated with the selected payment account option; transmitting, bythe one or more computing devices, the payment token to the point ofsale computing device for the point of sale computing device to processa payment transaction using the selected payment account option based onan issuer computing system associated with information in the paymenttoken.
 2. The method of claim 1, further comprising: at a time afteridentifying the digital wallet account of the user and at a time beforetransmitting the one or more payment account options, accessing, by theone or more computing devices, first user verification informationassociated with the digital wallet account; transmitting, by the one ormore computing devices and to the point of sale computing device, arequest for user verification information to be displayed on the pointof sale computing device; receiving, by the one or more computingdevices and from the point of sale computing device, second userverification information entered at the point of sale computing device;and determining, by the one or more computing devices, that the seconduser verification information matches the first user verificationinformation, and wherein transmitting the one or more payment accountoptions is performed in response to determining that the second userverification information matches the first user verificationinformation.
 3. The method of claim 2, wherein the first and second userverification information comprise one or more of biometric informationassociated with the user, a personal identification number, and apassword.
 4. The method of claim 1, wherein the user identificationinformation comprises an account number, a telephone number, an emailaddress, or a hardware identifier associated with a computing device ofthe user in proximity to the point of sale computing device.
 5. Themethod of claim 1, wherein the one or more payment account optionstransmitted to the point of sale device comprise payment accountinformation that is abbreviated or occluded.
 6. The method of claim 1,wherein the one or more payment account options comprise one or more ofa credit account, a debit account, a bank account, a coupon, a rewardspoints account, a voucher, and an account associated with the merchantsystem.
 7. A computer-implemented method to process a transaction viadigital wallet payment account information of a user at a point of salecomputing device of a merchant computing system, comprising; receiving,by a point of sale computing device associated with a merchant computingsystem, an input of a request to process a transaction using paymentinformation from a digital wallet account of a user; receiving, by thepoint of sale computing device, an input of user identificationinformation; transmitting, by the point of sale computing device and toone or more computing devices associated with the digital wallet accountof the user, the user identification information and a request forpayment account information associated with the digital wallet accountof the user; receiving, by the point of sale computing device and fromthe one or more computing devices, one or more payment account optionsassociated with the digital wallet account of the user; displaying, bythe point of sale computing device, the one or more payment accountoptions; receiving, by the point of sale computing device, an indicationof a selection of a particular payment account option from the one ormore particular payment account options displayed via the point of salecomputing system; transmitting, by the point of sale computing deviceand to the one or more computing devices, the indication of theselection of the particular payment account option; receiving, by thepoint of sale computing device and from the one or more computingdevices, a payment token associated with the particular payment accountoption; communicating, by the point of sale computing device and to anissuer computing system associated with the particular payment accountoption, a transaction authorization request and the payment token toprocess a payment transaction; receiving, by the point of sale computingdevice and from the issuer system, an authorization of the transactionauthorization request based on the particular payment option; andcompleting, by the point of sale computing device, the transaction basedon the received authorization.
 8. The method of claim 7, wherein the oneor more payment account options comprise one or more of a creditaccount, a debit account, a bank account, a coupon, a rewards pointsaccount, a voucher, and an account associated with the merchant system.9. The method of claim 7, further comprising: at a time before receivingthe one or more payment options, receiving, by the point of salecomputing device and from the one or more computing devices, a requestfor user verification information associated with the digital walletaccount of the user; displaying, by the point of sale computing device,the request for user verification information; receiving, by the pointof sale computing device, an input of user verification information; andtransmitting, by the point of sale computing device and to the one ormore computing devices, the received user verification information,wherein the one or more computing devices verify the transmitted userverification information against user verification information stored inassociation with the digital wallet account of the user, and whereinreceiving the one or more payment options from the one or more computingdevices is in response to the one or more computing devices verifyingthe user verification information.
 10. The method of claim 8, whereinthe received verification information comprises biometric information, apassword, or a personal identification number.
 11. The method of claim7, wherein receiving the user identification information comprises:establishing, by the point of sale computing device and with a usercomputing device in proximity to the point of sale computing device, anetwork connection; transmitting, by the point of sale computing deviceand to the user computing device, a request for a hardware identifierassociated with the user computing device; and receiving, by the pointof sale computing device and from the user computing device, a hardwareidentifier, wherein the user identification information transmitted tothe one or more computing devices comprises at least the hardwareidentifier.
 12. The method of claim 7, wherein receiving the useridentification information comprises: displaying, by the point of salecomputing device, a request for user identification information; andreceiving, by the point of sale computing device, an input of useridentification information entered via a user interface associated withthe point of sale computing device.
 13. A computer program product,comprising: a non-transitory computer-readable medium havingcomputer-readable program instructions embodied thereon that whenexecuted by a computer cause the computer to provide digital walletpayment account information of a user to a point of sale computingdevice of a merchant computing system, the computer-readable programinstructions comprising: computer-readable program instructions toreceive, from a point of sale computing device associated with amerchant computing system, user identification information associatedwith a user and a request for payment account information associatedwith a digital wallet account of the user; computer-readable programinstructions to identify the digital wallet account of the user based onthe received user identification information; computer-readable programinstructions to retrieve one or more payment account options associatedwith the digital wallet account of the user; computer-readable programinstructions to transmit, to the point of sale computing device, the oneor more payment account options for presentation by point of salecomputing device; computer-readable program instructions to receive,from the point of sale computing device, an indication of a selection atthe point of sale computing device of a particular payment accountoption from the one or more transmitted payment account options;computer-readable program instructions to generate, a payment tokenbased on payment account information associated with the selectedpayment account option; computer-readable program instructions totransmit, to the point of sale computing device, the payment token,wherein the point of sale computing device communicates the paymenttoken to an issuer computing system associated with the payment accountinformation to process a payment transaction using the selected paymentaccount option.
 14. The computer program product of claim 13, furthercomprising: computer-readable program instructions to access, at a timeafter identifying the digital wallet account of the user and at a timebefore transmitting the one or more payment account options, first userverification information associated with the digital wallet account;computer-readable program instructions to, to the point of salecomputing device, a request for user verification information to bedisplayed on the point of sale computing device; computer-readableprogram instructions to receive, from the point of sale computingdevice, second user verification information entered at the point ofsale computing device; and computer-readable program instructions todetermine that the second user verification information matches thefirst user verification information, and wherein transmitting the one ormore payment account options is performed in response to determiningthat the second user verification information matches the first userverification information.
 15. A computer program product, comprising: anon-transitory computer-readable medium having computer-readable programinstructions embodied thereon that when executed by a computer cause thecomputer to receive digital wallet payment account information of a userat a point of sale computing device of a merchant computing system, thecomputer-readable program instructions comprising: computer-readableprogram instructions to receive an input of a request to process atransaction using payment information from a digital wallet account of auser; computer-readable program instructions to receive an input of useridentification information; computer-readable program instructions totransmit, to one or more computing devices associated with the digitalwallet account of the user, the user identification information and arequest for payment account information associated with the digitalwallet account of the user; computer-readable program instructions toreceive, from the one or more computing devices, one or more paymentaccount options associated with the digital wallet account of the user;computer-readable program instructions to display the one or morepayment account options; computer-readable program instructions toreceive an indication of a selection of a particular payment accountoption from the one or more particular payment account options displayedvia the point of sale computing system; computer-readable programinstructions to transmit, to the one or more computing devices, theindication of the selection of the particular payment account option;computer-readable program instructions to receive, from the one or morecomputing devices, a payment token associated with the particularpayment account option; computer-readable program instructions tocommunicate, to an issuer computing system associated with theparticular payment account option, a transaction authorization requestand the payment token to process a payment transaction;computer-readable program instructions to receive, from the issuersystem, an authorization of the transaction authorization request basedon the particular payment option; and computer-readable programinstructions to complete the transaction based on the receivedauthorization.
 16. The computer program product of claim 15, furthercomprising: computer-readable program instructions to receive, at a timebefore receiving the one or more payment options and from the one ormore computing devices, a request for user verification informationassociated with the digital wallet account of the user;computer-readable program instructions to display the request for userverification information; computer-readable program instructions toreceive an input of user verification information; and computer-readableprogram instructions to transmit, to the one or more computing devices,the received user verification information, wherein the one or morecomputing devices verify the transmitted user verification informationagainst user verification information stored in association with thedigital wallet account of the user, and wherein receiving the one ormore payment options from the one or more computing devices is inresponse to the one or more computing devices verifying the userverification information.
 17. A system to provide digital wallet paymentaccount information of a user to a point of sale computing device of amerchant computing system, comprising: a storage device; and a processorcommunicatively coupled to the storage device, wherein the processorexecutes application code instructions that are stored in the storagedevice to cause the system to: receive, from a point of sale computingdevice associated with a merchant computing system, user identificationinformation associated with a user and a request for payment accountinformation associated with a digital wallet account of the user;identify the digital wallet account of the user based on the receiveduser identification information; retrieve one or more payment accountoptions associated with the digital wallet account of the user;transmit, to the point of sale computing device, the one or more paymentaccount options for presentation by point of sale computing device;receive, from the point of sale computing device, an indication of aselection at the point of sale computing device of a particular paymentaccount option from the one or more transmitted payment account options;generate, a payment token based on payment account informationassociated with the selected payment account option; and transmit, tothe point of sale computing device, the payment token, wherein the pointof sale computing device communicates the payment token to an issuercomputing system associated with the payment account information toprocess a payment transaction using the selected payment account option.18. The system of claim 17, wherein the one or more payment accountoptions comprise one or more of a credit account, a debit account, abank account, a coupon, a rewards points account, a voucher, and anaccount associated with the merchant system.
 19. A system to receivedigital wallet payment account information of a user at a point of salecomputing device of a merchant computing system, comprising: a storagedevice; and a processor communicatively coupled to the storage device,wherein the processor executes application code instructions that arestored in the storage device to cause the system to: receive an input ofa request to process a transaction using payment information from adigital wallet account of a user; receive an input of useridentification information; transmit, to one or more computing devicesassociated with the digital wallet account of the user, the useridentification information and a request for payment account informationassociated with the digital wallet account of the user; receive, fromthe one or more computing devices, one or more payment account optionsassociated with the digital wallet account of the user; display the oneor more payment account options; receive an indication of a selection ofa particular payment account option from the one or more particularpayment account options displayed via the point of sale computingsystem; transmit, to the one or more computing devices, the indicationof the selection of the particular payment account option; receive, fromthe one or more computing devices, a payment token associated with theparticular payment account option; communicate, to an issuer computingsystem associated with the particular payment account option, atransaction authorization request and the payment token to process apayment transaction; receive, from the issuer system, an authorizationof the transaction authorization request based on the particular paymentoption; and complete the transaction based on the receivedauthorization.
 20. The system of claim 19, wherein receiving the useridentification information comprises: establishing, with a usercomputing device in proximity, a network connection; transmitting, tothe user computing device, a request for a hardware identifierassociated with the user computing device; and receiving, from the usercomputing device, a hardware identifier, wherein the user identificationinformation transmitted to the one or more computing devices comprisesat least the hardware identifier.